home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20030409-20031118
/
000162_fdc@columbia.edu_Sun Jun 15 12:45:01 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2003-11-18
|
4KB
|
100 lines
Article: 14391 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Backspace Insists on sending ^H
Date: 15 Jun 2003 12:36:51 -0400
Organization: Columbia University
Lines: 83
Message-ID: <bci7b3$plv$1@watsol.cc.columbia.edu>
References: <779oev84tluh03lpoag0imeueh45algboj@4ax.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1055695012 15418 128.59.39.139 (15 Jun 2003 16:36:52 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 15 Jun 2003 16:36:52 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14391
In article <779oev84tluh03lpoag0imeueh45algboj@4ax.com>,
Ron Heiby <heiby_u@falkor.chi.il.us> wrote:
: Based on the amount of documentation of Backspace / Delete / Keyboard
: issues, I am sure that I am not the only one confused by this area of
: endeavor. But, I have read an awful lot of documentation that sounds like
: it should be helping me figure this out, but I'm still not successfully
: sending the character I want to send.
:
: I've constructed a dialer entry to connect me with a system in my lab. I
: have told it to use vt320 emulation, and sure enough, my Linux session
: thinks I'm on a vt320.
:
But this does not affect what the remote Unix system's erase character is.
: In the "Keyboard" setup area, I have told Kermit
: that "Backspace key sends Delete (Rubout)". In the script generated by
: the dialer (below), I see a line that says, "set dialer backspace \127",
: which looks like it probably is intended to cause Kermit to send a DEL
: when I press my PC's [<- Backspace] key.
:
In K95, which (unlike C-Kermit) supports multiple terminal types with a
separate keymap for each, this performs the equivalent of "set key \264 \127"
for each terminal type, because this is a keyboard setting and not a
terminal-specific setting, thus applies to the keyoard independently of
the terminal type. OK, so..
: However, the character that gets
: sent is a BS (^H). If I enter the Kermit command "show key one" and press
: that key, I am told, "Key code \264 Backspace (default) => Character:
: \8". This sure looks like it wants to send a BS when I press that key,
: despite the "set dialer backspace \127" command.
:
Doesn't happen here.
: At this point, it looks like the dialer configuration for the backspace
: key does nothing.
:
The default setting is \127. A command must have been executed that changed
it from this to \8.
: But, I find that hard to believe, as *someone* would
: have noticed before now. It does look like I am able to add an explicit
: "set key" to get the backspace key to emit a DEL, which seems an OK
: workaround.
:
Where do you add it?
Either:
(a) You're doing something that overrides the Dialer's setting; or:
(b) There's something you didn't tell us; or:
(c) I'm missing something; or:
(d) There's a bug.
When Kermit 95 starts, commands are executed in the following order:
certain "pre-scanned" command-line options
k95.ini
k95site.ini
k95custom.ini
Any command-line options that were not pre-scanned
Dialer script
Interactive commands or scripts explicitly invoked
The Dialer script itself can execute two other scripts if you tell it:
The keyboard script (selected on the Keyboard Settings page)
The login script (selected from the Login page)
If you have specified either one of these scripts, and it contains a SET
KEY command, this can override the Enter and Backspace key settings on
the Keyboard Settings page.
However, the Dialer script you sent did not include any TAKE commands.
Therefore it's not obvious why this happens to you but not to me. I think
more evidence is needed. Did you execute any other command files or macros
after the connection was made that might have changed the key setting?
The way that you worked around this by adding "set key" to a file should
provide a good clue.
- Frank